Uninstalling using the IBM Installation Manager

The first step to follow when you are uninstalling a WAS based Sametime component is to run the uninstaller in the IBM Installation Manager. Before doing this make sure your the server you want to uninstall is fully stopped, and all WAS process are not running.

To uninstall, launch IBM Installation manager and on the main screen choose the uninstall option (see figure 1).

Figure 1 – Uninstall via Installation Manager

 

After selecting Uninstall you then need to select the server you wish to uninstall and click 'Next'. Figure 2 shows an example of uninstalling a Sametime Proxy server.

Figure 2 – Uninstall Sametime Proxy Server

Finally click uninstall and wait for the Installation Manager to complete the uninstall procedure.

Cleaning up the machine after Uninstall

After the uninstaller has complete, the next step is to manually remove files that were used by the WAS Sametime component. The best way to do this is to simply delete the WebSphere home folder. If you have other Websphere products installed on the machine, go into the WebSphere folder and just remove the ones used by the Sametime Component.

The default location of the WebSphere home folder on Windows is 'C:\Program Files\IBM\WebSphere' and Linux is '\opt\IBM\WebSphere'.

NOTE: If using 64 bit Windows the default is 'C:\Program Files (x86)\IBM\WebSphere'

Cleaning up the deployment manager after Uninstall

This step is only needed if your deployment is a federated deployment (i.e each Sametime component uses the same deployment manager). If you have a cell deployment (ie each Sametime component has its own deployment manager), you do not have to worry about this step because the uninstall process in Chapter 1 will remove the deployment manager as well as the Application server.

There are 4 places you need to clean up in your deployment manager to fully remove any evidence that the uninstalled application ever existed.

Delete WebSphere application server

1. Log into your deployment manager and navigate to Servers → Server Types → WebSphere application servers.

2. Check the tick box beside the server you have uninstalled and click the delete button. Figure 3 shows the deletion of the STProxyServer.

   Figure 3 – Delete STProxyServer application server

Uninstall WebSphere enterprise application(s)

i.In your deployment manager navigate to Applications → Application Types → WebSphere enterprise applications.
ii.Check the tick box beside any of the enterprise applications that are used by the application server you have uninstalled. Then click the Uninstall button. Figure 4 shows a list of all of the enterprise applications and what server they are used by.

Figure 4 – List of enterprise applications

NOTE: The DefaultApplication.ear is used as a SNOOP servlet. It can be used on any of the Application servers. You can find out which server it was installed to by clicking on the name of the enterprise application and under Modules, go to the 'Manage Modules' link (see Figure 5).

Figure 5 – Manage Modules

 

Delete Bus(es)

This step is only necessary if you are uninstalling a Sametime Meeting server or a Sametime Advanced server. Log in to your deployment manager (SSC) and go to Servive Integration > Buses. Tick the bus(es) that are used by the application server you have uninstalled and click Delete. Figure 6 shows a list of the buses and the server they are used by.

Figure 6 – List of Buses

Delete Node

 

The last step is to make sure that the node has been removed from the deployment manager. To do this:

1. Log in to your deployment manager and navigate to System administration → Nodes.

2. Check to see if the node still exists for the application server you have uninstalled. If it does select the tick box beside it and click 'Force Delete' (see Figure 7).

   Figure 7 – Delete Node

Conclusion

You should now be able to cleanly uninstall any WAS based Sametime component.

About the authors

Conall O'Cofaigh is a Software Engineer working on the Sametime Verification Test team. He's been with IBM since 2008, focusing on integration and interoperability across Lotus Sametime products.